Setting up Active Storage Manager: Oracle

This section discusses how to set up Active Storage Manager for Oracle. For information on how to set up Active Storage Manager for SQL Server, see Setting up Active Storage Manager: SQL Server.

Note: Active Storage Manager expects the TableSpace to follow the IEE Standard TableSpace Naming Conventions. The TableSpace Naming Conventions can be found in the AddReadingPartitions.pls script delivered with the 10.3 Installer. TableSpace names are case insensitive and are always stored as uppercase even if referenced in mixed case. For more information, see Active Storage Manager in the IEE MDM Help.

General Constraints, Assumptions, Dependencies, and Guidelines

  • Storage locations are accessible to move the database files.

  • Storage locations have sufficient storage space.

  • Two instances of Active Storage Manager cannot be run at the same time.

Prerequisites

Setting up IEE Active Storage Manager requires the following prerequisites:

  • Oracle Advanced Compression option licensed and enabled on the target databases.

  • File systems (or ASM Disk Groups) provisioned for Storage Tier 2 (and Storage Tier 3, if desired).

  • Oracle system/DBA user credentials (for creation of Storage Tier 2 (and Storage Tier 3, if desired) tablespaces.

  • IEE schema owner database credentials (for IEE version 10.0 and higher).

  • Desired values for retention period, data area suffix, compression level, and read-only for Storage Tier 2 (and Storage Tier 3, if desired).

To configure the IEE Active Storage Manager task template:

  1. Open the IEE Rich Client application.

  2. Go to System Operations > Task Management > Task Templates.

  3. From the Task Type dropdown menu, choose Active Storage Manager.

  4. Enter desired values for the DefaultActiveStorageManager template. Refer to Configuring the task template and parameters: Oracle for definitions and requirements for the parameters.

    Important! Currently, IEE Active Storage Manager only supports using the DefaultActiveStorageManager template. Do not create any additional templates.

  5. Click Save.

  6. Identify tier 2 (and tier 3, if configured) tablespaces needing to be created.

    1. Using the SQL Client of your choice (SQLPlus, sqlcl, etc.) connect to the Oracle database as the IEE schema owner.

    2. Use the active_storage_manager.prepare_tablespaces stored procedure. The procedure supports these parameters:

      • p_tier2_path – the physical path where tier 2 datafiles are stored (default: <TIER2_PATH>)

      • p_tier3_path – the physical path where tier 3 (if configured) datafiles are stored (default: <TIER3_PATH>)

      • p_use_bigfile – should bigfile tablespace commands be generated (YES or NO, default: NO)

    3. Execute these commands (parameters shown are an example; replace with your desired parameters):

      set serveroutput on size unlimited;

      exec active_storage_manager.prepare_tablespaces(p_tier2_path => '/path/to/tier/2/'

      ,p_use_bigfile => 'no');

      set serveroutput off;

    4. The script produces output of a set of CREATE TABLESPACE commands for tier 2/3 tablespaces, which will be needed to effect the archiving of data according to the template parameters defined in step 3 above:

      CREATE TABLESPACE DCL_Y2020_M02_T2 DATAFILE '/path/to/tier/2/dcl_y2020_m02_t201.dbf' SIZE 10304K AUTOEXTEND ON NEXT 64K LOGGING EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO;

      CREATE TABLESPACE DCL_Y2020_M03_T2 DATAFILE '/path/to/tier/2/dcl_y2020_m03_t201.dbf' SIZE 10304K AUTOEXTEND ON NEXT 64K LOGGING EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO;

      CREATE TABLESPACE DCL_Y2020_M04_T2 DATAFILE '/path/to/tier/2/dcl_y2020_m04_t201.dbf' SIZE 10304K AUTOEXTEND ON NEXT 64K LOGGING EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K SEGMENT SPACE MANAGEMENT AUTO;

      Alternatively, the DBA may choose to provision partition tablespaces manually for entire years at a time.

      Note: No tablespaces will be created by the script. It is the DBA's responsibility to modify and execute the generated commands according to the standards set by the customer. Itron recommends sizing tier 2 and tier 3 tablespaces very small and allowing them to autoextend as data are migrated to them.